bad-expr-lhs.rs -> destructuring-assignment
bad-expr-path.rs -> resolve
bad-expr-path2.rs -> resolve
bad-crate-name.rs -> parser
bad-extern-link-attrs.rs -> linkage-attr
bad-mid-path-type-params.rs -> generics, probably
bad-env-capture(1,2,3).rs -> resolve
bad-type-env-capture.rs -> resolve
bad-module.rs -> resolve
bad-method-typaram-kind.rs -> traits
bad-sized.rs -> traits

(The list largely matches suggestions from classifui.)
Tidy also needs to be updated.

Subdirectories like expr or fn are almost as meaningless as bad, TBH.
I'm trying to classify tests by compiler areas, because compiler areas in their turn map on people who will maintain tests in a given subdirectory.
Let's say, I'm maintaining name resolution and want to bring some order to name resolution tests, remove garbage and duplicates, etc. (Const eval working group may want to do the same things with constant evaluation, etc.). Then we'll know where to find relevant tests.

Thanks for the review @petrochenkov. All provided information will surely help in the next PR.

@bors r+

📌 Commit 4e6d6ab has been approved by petrochenkov

⌛ Testing commit 4e6d6ab with merge 6765010...

☀️ Test successful - checks-actions
Approved by: petrochenkov
Pushing 6765010 to master...